The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Design database
|
|
Review organisational and task requirements to confirm scope and functionality of database design, including data redundancy Completed |
Evidence:
|
Develop a logical data model to identify and classify data into types Completed |
Evidence:
|
Select appropriate software according to organisational and task requirements and required scope and functionality of database Completed |
Evidence:
|
Confirm database design with appropriate person Completed |
Evidence:
|
Develop database
|
|
Set field attributes according to data type and link databases by a common field in accordance with software procedures Completed |
Evidence:
|
Identify primary key to uniquely identify data Completed |
Evidence:
|
Identify foreign keys to establish associations between data Completed |
Evidence:
|
Use software functions and formulae to meet organisational and task requirements Completed |
Evidence:
|
Create password and access system according to organisational and task requirements Completed |
Evidence:
|
Develop queries, forms and reports
|
|
Develop queries as required by organisational and task requirements Completed |
Evidence:
|
Develop input screens or forms in order to access required data Completed |
Evidence:
|
Develop reports according to organisational and task requirements Completed |
Evidence:
|
Test and finalise database
|
|
Populate database with sample dataset for testing Completed |
Evidence:
|
Assess and document effectiveness of data relationships, queries forms and reports Completed |
Evidence:
|
Address any errors in database design Completed |
Evidence:
|
Name and store database in accordance with organisational requirements and exit the application without data loss or damage Completed |
Evidence:
|
Confirm database readiness with appropriate person Completed |
Evidence:
|